refactor(core): simplify persistence boundaries - #43929
Merged
Merged
Conversation
kitlangton
enabled auto-merge (squash)
August 21, 2026 17:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Simplify persistence and external-data boundaries by reusing canonical connection, filtering, normalization, and narrowing primitives. The refactor removes duplicated implementation while preserving every query, transaction, path, error, and provider-overlay behavior.
How
Sqlite.makeConnectionhelper used by Bun and Node.allandlist.isRecordguard for provider overlays.Scope
Behavior-preserving Core cleanup only; no schema, migration, transaction, path policy, MCP recovery, provider merge, or public API changes.
Testing
bun run test test/ripgrep.test.ts(6 passed)bun typecheckfrompackages/corebun turbo typecheck --concurrency=3(40-package workspace)